Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces several enhancements to the primary
Dockerfile
including:/etc/passwd
to run aphrodite-engine/home/aphrodite-engine
and avoid permission issuesapt-get clean
to (slightly) reduce layer sizeENTRYPOINT
with APP_HOMENo application paths were changed as part of this enhancement to maintain backwards compatibility, however please be aware that
/aphrodite-engine
is now read only.Motivation
When loading a GPTQ quantized version of CommandR+, aphrodite-engine exited after building the KV cache with the following message: "KeyError: 'getpwuid(): uid not found: 1000'". The root cause was ultimately running the process under a UID that didn't have a corresponding entry in
/etc/passwd
. I'm not clear why this wasn't happening with other models I've tested with.As stated above, this introduces a better design where the service account user's home directory is different than the application directory. This allows any dotfiles (such as
.cache
) created by that user to reside outside the main application directory.